feat: update Next.js to 16.2.1 and eslint-config-next#3
feat: update Next.js to 16.2.1 and eslint-config-next#3recoupableorg wants to merge 1 commit intomainfrom
Conversation
Upgrades Next.js from 16.0.10 to 16.2.1 (stable release). No breaking changes per release notes — new features include browser log forwarding, dev server lock file, and agent-ready scaffolding. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
📝 WalkthroughWalkthroughDependencies for Next.js and ESLint configurations were updated across two applications. The Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/web/package.json`:
- Line 35: Update the pinned eslint dependency from "^8" to "^9" to satisfy
eslint-config-next@16.2.1's peer requirement: edit the package.json entries for
the "eslint" field in both the apps/web and apps/ops projects and set "eslint":
"^9"; after changing the version run your package manager to refresh lockfiles
(npm/yarn/pnpm) and verify linting (npm run lint) to confirm no other peer
conflicts remain.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e6462071-ee6f-4ef1-83a8-60add3632c64
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
apps/ops/package.jsonapps/web/package.json
| "@types/react-dom": "^18", | ||
| "eslint": "^8", | ||
| "eslint-config-next": "14.2.13", | ||
| "eslint-config-next": "16.2.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== Local versions in apps/web/package.json =="
jq -r '.devDependencies | {eslint, "eslint-config-next": ."eslint-config-next"}' apps/web/package.json
echo
echo "== Local versions in apps/ops/package.json =="
jq -r '.devDependencies | {eslint, "eslint-config-next": ."eslint-config-next"}' apps/ops/package.json
echo
echo "== Peer deps from npm registry for eslint-config-next@16.2.1 =="
curl -s https://registry.npmjs.org/eslint-config-next/16.2.1 | jq '.peerDependencies'Repository: recoupable/marketing
Length of output: 384
Upgrade eslint to ^9 to satisfy eslint-config-next@16.2.1 peer dependency.
eslint-config-next@16.2.1 requires eslint >= 9.0.0 as a peer dependency, but Line 34 pins eslint to ^8. This will cause installation or linting failures. Update both apps/web and apps/ops to use eslint: "^9".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/web/package.json` at line 35, Update the pinned eslint dependency from
"^8" to "^9" to satisfy eslint-config-next@16.2.1's peer requirement: edit the
package.json entries for the "eslint" field in both the apps/web and apps/ops
projects and set "eslint": "^9"; after changing the version run your package
manager to refresh lockfiles (npm/yarn/pnpm) and verify linting (npm run lint)
to confirm no other peer conflicts remain.
1 participant
Upgrades Next.js from 16.0.10 to 16.2.1 (stable release). No breaking changes per release notes — new features include browser log forwarding, dev server lock file, and agent-ready scaffolding.
Summary by CodeRabbit